---
title: "Get payment"
method: GET
path: "/payments/{id} "
---

# Get payment

`GET /payments/{id} `

## Path parameters

- `id` string, required

## Headers

- `Host` string, required
- `Date` string, required
- `Digest` string, required
- `Authorization` string, required
- `x-satispay-response-wait-time` integer
- `x-satispay-deviceinfo` string
- `x-satispay-devicetype` 'SMARTPHONE' | 'TABLET' | 'CASH REGISTER' | 'POS' | 'PC' | 'ECOMMERCE_PLUGIN'
- `x-satispay-os` string
- `x-satispay-osv` string
- `x-satispay-apph` string
- `x-satispay-appn` string
- `x-satispay-appv` string
- `x-satispay-tracking-code` string

## Response `200`

OK

- object
  - `id` string — The unique payment id. <br> <br> This can be used for every eventual subsequent operations on the payment, including refunds.
  - `code_identifier` string — The Satispay code identifier. <br> <br> This string can be encoded in a QR code that can be scanned by the user. <br> This property is only available in `MATCH_CODE` flow payments.
  - `type` string — The current payment type. <br> <br> `TO_BUSINESS` <br> This type is used for payments from a consumer to a merchant. <br> <br> `REFUND_TO_BUSINESS` <br> This type is used for payments from a merchant to a consumer (e.g. refunds).
  - `amount_unit` integer — The payment amount in cents. <br> <br> For example, the amount `€12.40` is being represented as `1240` cents.<br> <br> When using the parameter `payment_options.partial_payment` = `true` <br> this final amount could change when the payment will transition to `ACCEPTED` status.
  - `currency` 'EUR' — The payment currency.
  - `status` string — The current payment status. <br> <br> `PENDING` <br> The payment is created and awaits user interaction, such as scanning the QR code. <br> <br> `ACCEPTED` <br> The payment has been accepted and succesfully executed. <br> <br> `CANCELED` <br> The payment has been canceled, this could happen if: <br> - the consumer's explicitely declines it in the Satispay app. <br> - the merchant cancels it via the [Update payment API](https://developers.satispay.com/reference/mv-update-payment) with a `CANCEL` action. <br> - the payment reaches the `expiration_date` while in a `PENDING` status.
  - `status_ownership` boolean
  - `expired` boolean — The current payment expiration status. <br> <br> It becomes `true` once it reaches the `expiration_date` without being accepted or canceled.
  - `metadata` object — The additional metadata for the payment.
  - `sender` object — The sender payment actor.
    - `id` string — The unique sender id. <br> <br> This will only be available once the payment will be matched with a consumer.
    - `type` string — The sender type. <br> <br> `CONSUMER` <br> This sender type is used when the payment goes from a consumer to a merchant. <br> <br> `SHOP` <br> This sender type is used when the payment goes from a merchant to a consumer (e.g. refunds payments).
    - `name` string — The sender name. <br> <br> This will only be available once the payment will be matched with a consumer.
  - `receiver` object — The receiver payment actor.
    - `id` string — The unique receiver id.
    - `type` string — The receiver type. <br> <br> `CONSUMER` <br> This receiver type is used when the payment goes from a merchant to a consumer. <br> <br> `SHOP` <br> This receiver type is used when the payment goes from a consumer to a merchant (e.g. refunds payments).
  - `insert_date` string — The UTC payment creation datetime.
  - `expire_date` string — The UTC payment expiration datetime.
  - `description` string — The external_code set during the payment creation request. <br> <br> Please use the `external_code` field instead.
  - `flow` string
  - `external_code` string — The `external_code` set during the creation request.
  - `redirect_url` string — The URL where to redirect the user to begin the Satispay payment flow. <br> <br> This property is available only when the payment uses the `MATCH_CODE` flow.
  - `payment_method` object
    - `meal_voucher` object — The Meal Voucher payment part. <br> <br> This property is available only when: <br> - the payment is `ACCEPTED`. <br> - the payment contains Meal Vouchers in it.
      - `amount_unit` integer — The total amount of Meal Vouchers in this payment, in cents. <br> <br> For example, the amount `€8.00` is being represented as `800` cents.
      - `number` integer — The total number of Meal Vouchers in this payment. <br> <br> As per italian law, it can't be higher than `8` Meal Vouchers per payment.

## Other responses

- `401` — 401 Unauthorized
- `403` — 403 Forbidden or invalid authorization header
- `404` — 404 Resource not found

---

[API](https://skmtc.net/satispay/apis/satispay-gbusiness-api.md) · [All operations](https://skmtc.net/satispay/apis/satispay-gbusiness-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/satispay/satispay-gbusiness-api/versions/f91f20a37e6f/schema)